Apparatus And Method To Protect Digital Content

ABSTRACT

In an embodiment of the present invention, a processor includes content storage logic to parse digital content into portions and to cause each portion to be stored into a corresponding page of a memory. The processor also includes protection logic to receive a write instruction having a destination address within the memory, and if the destination address is associated with a memory location stores a portion of the digital content, erase the page associated with the memory location. If the destination address is associated with another memory location that does not store any of the digital content, the protection logic is to permit execution of the write instruction. Other embodiments are described and claimed.

TECHNICAL FIELD

The technical field is protection of digital content.

BACKGROUND

Encrypted digital content may be vulnerable to attack after decryption.For example, an overwrite of a portion of the decrypted digital contentmay constitute an attack. In an attack, a write instruction may bedirected to overwrite a data type indicator that indicates whethersubsequent data in a data string is metadata or payload data. Overwriteof the data type indicator, from an indication of payload data to anindication of metadata, may permit unauthorized access to the payloaddata. That is, because the data stored in locations subsequent to thedata type indictor is re-labeled as metadata instead of payload data,and because metadata is not typically protected, the (incorrectlylabeled) payload data may be subject to unauthorized access that mayinclude theft of the payload data.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a portion of a system in accordance with anembodiment of the present invention.

FIG. 2 is a block diagram of a portion of another system in accordancewith an embodiment of the present invention.

FIG. 3 is a block diagram showing digital content written in a memory,according to an embodiment of the invention.

FIG. 4 is a flow diagram of a method of protecting digital content,according to an embodiment of the present invention.

FIG. 5 is a block diagram of a processor core in accordance with anembodiment of the present invention.

FIG. 6 is a block diagram of a processor in accordance with anembodiment of the present invention.

FIG. 7 is a block diagram of a multi-domain processor in accordance withan embodiment of the present invention.

FIG. 8 is an illustration of an embodiment of a processor includingmultiple cores in accordance with an embodiment of the presentinvention.

FIG. 9 is a block diagram of a system in accordance with an embodimentof the present invention.

FIG. 10 is a block diagram of a system in accordance with anotherembodiment of the present invention.

DETAILED DESCRIPTION

A Security Enhanced Processor (SEP) may be used for secure contentdecryption, e.g., during a digital rights management (DRM) playback.Content may be decrypted into Isolated Memory Regions (IMR), a dedicatedmemory with access control mechanisms that may be built into associatedhardware. IMR usage may prevent a host processor and malware from directaccess to the decrypted content and may permit only selected subsystems(e.g., secure engines and a hardware decoder) to access the contentstored in the IMR.

The decoder may need information about protected compressed contentbefore the decoder can proceed to decode. For example, information aboutthe size and location of slice metadata and actual protected contentpayload may be needed prior to the decoder decoding the compressed data.This opens up potential for security holes, e.g. “cut and paste attack”and “plain text overlay.” For example, due to an attack when the data isparsed by the security engine, the entire decrypted content (including aprotected PAYLOAD) may be provided to the host entity since the securityengine mistakenly interprets the data as metadata based on modificationof header information. Thus, the protected payload content could bestolen by a rogue application in the host.

Additionally, smaller packets that are not crypto-block aligned canarrive as plain-text material from the content provider, and the hostcan specify to the security engine that a packet does not needdecryption. Therefore, the attacker may specify the “overwritten plaintext part” as content not needing decryption. Note that security enginegets the location information (through an offset) from the host.Consequently the host can potentially send incorrect data this way toreplace the actual data.

The attack scenario is possible for those schemes that can sendirregular sized packets that are not aligned with actual video frames.Attack is also possible on hardware platforms whose decoders do not haveability to parse the entire streams themselves.

In an example, the attack may be directed to data that has already beendecrypted into the IMR. In some platforms that support IMR, only thesecurity engine has READ-WRITE access to IMRs, while other components,e.g., the decoder, are limited to READ-ONLY access. The security enginemay lock the decrypted data so that it is only consumed by subsequentsecure video path components to potentially eliminate “overwrite”attacks, and may reset (e.g., unlock) after consumption.

However, the security engine may not be aware of when a given data isconsumed. Moreover, the IMR can hold multiple frames before each frameis consumed by the decoder. Hence, data writes, e.g., by the securityengine, and data reads, e.g., by the decoder, can happen in an arbitraryfashion.

Typically, a frame is decrypted in its entirety before it is consumed,and multiple packets that constitute a frame are fed into the securityengine in contiguous fashion. That is, a frame can be made up ofmultiple packets and these packets are decrypted contiguously into theIMR until the entire frame is decrypted into the IMR before packets ofanother frame are decrypted.

In an embodiment of the present invention, the IMR may provide awrite-lock-reset facility, e.g., on a per page (or a per block)granularity. A page (or block) can have any granularity, per the systemneeds. The page can be configured at system start up. A running OFFSETof a last offset within a page written to may be maintained in a storageregister associated with the page. The OFFSET may be updated on everywrite as follows: If the new offset is greater than the OFFSET, writesare permitted and the OFFSET may be updated to last location written to.In other words, the OFFSET is “locked” by the storage register. Ifwrites are attempted to an offset within the page that is less than theOFFSET, then the OFFSET may be reset to zero (page UNLOCKED), the pagemay be erased, and new writes may be permitted to any offset within thepage. After the writes, the OFFSET may be updated again.

An offset less than OFFSET may be attempted in two cases: 1) A new frameis being written/decrypted into the IMR. In this case, typically resetof the OFFSET and unlock of the page occurs. 2) A malware attempts tomodify the existing data, in which case reset of the OFFSET andclearance (e.g., erasure) of the entire page can prevent themodification.

The page size can be made adjustable or configurable to fit the framesize. In one example, the entire frame may be cleared when an attack isdetected, e.g., by comparison of the write offset to the OFFSET storedin the storage register.

In an embodiment, LOCK-and-RESET functionality can be implemented infirmware, or in hardware. For instance, the firmware running on the SEPcan maintain page attributes (e.g., last written offset) and mimicLOCK-and-RESET functionality in software. Since SEP firmware is expectedto run in a secure environment, the results are equally effective whenimplemented in hardware.

In various embodiments, protection of digital content may be provided bya processor, e.g., after the digital content has been decrypted. Theprocessor may include content storage logic to parse the digital contentinto portions and to store each portion into a corresponding page of amemory. The processor may also include protection logic to receive awrite instruction that includes a destination address, after the parseddigital content is stored, and if the destination address of the writeinstruction is to a memory location that stores a portion of the digitalcontent, the protection logic may erase the page. If the destinationaddress is associated with another memory location that does not storeany of the digital content, the protection logic may execute the writeinstruction. Erasure of a page whose stored digital content is targetedby the write instruction may protect the erased digital content frombeing accessed by an unauthorized party.

Referring now to FIG. 1, shown is a block diagram of a portion of asystem 100 in accordance with an embodiment of the present invention. Asshown in FIG. 1, the system 100 may include various components,including a Security Enhanced Processor (SEP) 102.

The SEP 102 may include decryption logic 112 to decrypt incominginstructions. The SEP 102 may include a memory controller hub (MCH) 110that may include content storage logic 114 and protection logic 116 thatmay include address storage logic, 118, address comparison logic 120,and page erase logic 122. The MCH 110 may also include one or morestorage registers 124 ₀, 124 ₁, . . . , 124 _(n) to store an addressoffset, e.g., offset of a last written memory location within acorresponding page. Note that in FIG. 1 the SEP 102 is depicted at ahigh level and it is to be understood that a processor such as the SEP102 may include many other features.

The system 100 may also include a memory 150, which may be anaccess-controlled memory including one or more isolated memory regions(IMR). In various embodiments, the memory 150 may be dynamic randomaccess memory (DRAM), static random access memory (SRAM), or anothertype of storage memory. Access to the IMR may be determined by the MCH110.

The memory 150 may be coupled, through the MCH 110, to a decoder 180. Inan embodiment, the decoder 180 may be situated on a motherboard (notshown), e.g., along with the SEP 102 and the memory 150.

A portion of the memory 150 may be divided into one or more pages 154 ₀,154 ₁, . . . , 154 _(n). In an embodiment, each page may have the samestorage capacity, e.g., approximately 4 kilobytes (kB), or anotherstorage capacity. In another embodiment, one or more of the pages 154₀-154 _(n) may vary in storage capacity from other of the pages 154₀-154 _(n).

In operation, the SEP 102 may receive encrypted digital content 160 andthe decryption logic 112 may decrypt the encrypted digital content 160to produce (unencrypted) digital content.

After the encrypted digital content has been decrypted, the contentstorage logic 114 in the MCH 110 may parse the digital content into oneor more portions, e.g., each portion corresponding to one of the pages154 ₀, 154 ₁, . . . , 154 _(n) of the memory 150. In some embodiments,the portions may be of equal size. In other embodiments, at least oneportion may differ in size from other portions. After the decryptedcontent is parsed into portions, the portions may be stored by thecontent storage logic 114, with each portion stored into a correspondingpage 154 ₀, 154 ₁, . . . , 154 _(n).

The address storage logic 118 may store an address of a last writtenmemory location within each of the pages 154 ₀, 154 ₁, . . . , 154 _(n)into a corresponding storage register 124 ₀, 124 ₁, . . . , 124 _(n) asan offset from a starting address of the corresponding page.

The SEP 102 may receive program instructions 170. One of the programinstructions may be a write instruction directed to a destinationaddress that is within one of the pages 154 ₀, 154 ₁, . . . 154 _(n).The MCH 110 may determine which page 154 _(i) includes the destinationaddress of the write instruction. The address comparison logic 120 maycompare a representation of the destination address of the writeinstruction with a representation of the address stored in a storageregister 124 _(i) corresponding to page 154 _(i). For example, theaddress comparison logic 120 may determine that an offset correspondingto the destination address of the write instruction is less than orequal to the offset stored in the storage register 124 _(i) thatcorresponds to the last written address of the page 154 _(i). Ifexecuted, the write instruction would overwrite some of the stored datain page 154 _(i). For example, the stored data that is targeted to beoverwritten may include a data indicator type of the payload data. Ifthe data indicator type were to be overwritten, the payload data mightbe mistakenly labeled as, e.g., metadata, which is typically notprotected, and so the payload data might be subject to attack.

If it is determined that the destination address is less than or equalto the address represented by the offset stored in the storage register124 _(i), the address comparison logic 120 may trigger the page eraselogic 122 to erase the page 154 _(i). Erasure of the page 154 _(i) canensure that digital content stored in the page will not be subject tounauthorized access. In an embodiment, subsequent to erasure the page154 _(i) may be left blank.

If the destination address of the received write instruction is greaterthan the stored address in the storage register 124 _(i) the writeinstruction may be executed, e.g., additional data may be written to thepage 154 _(i), e.g., to an unwritten portion of the page 154 _(i).

Contents of the pages 154 ₀, 154 ₁, . . . , 154 _(n) can be provided tothe decoder 180 via the MCH 110 for decoding, and the decoded data maybe output, e.g., as video, audio, or other proprietary content. In anattack scenario, a page 154 _(i) may be erased and decoded as noise andmay be output as noise that may serve to indicate that the digitalcontent 162 has been attacked.

Turning now to FIG. 2, shown is a block diagram of a portion of a system200 in accordance with another embodiment of the present invention. Asshown in FIG. 2, the system 200 may include various components,including a processor 210 that may be coupled to a memory controller hub(MCH) 222. The processor 210 may be a multi-core processor that mayinclude cores 211 ₀, 211 ₁, . . . , 211 _(n). The processor 210 may alsoinclude decryption logic 212 to decrypt encrypted digital content.

The MCH 222 may be coupled to a memory 220, such as a dynamic randomaccess memory (DRAM), static random access memory (SRAM), or anothertype of memory. The MCH 222 may include content storage logic 224 andprotection logic 226 that may include address storage logic 228, addresscomparison logic 230, and page erase logic 232. The MCH 222 may alsoinclude one or more storage registers 242 ₀, 242 ₁, . . . , 242 _(n),each to store an address of a page in the memory 220, e.g., as an offsetfrom an initial address of the corresponding page.

The memory 220 may be divided into one or more pages 240 ₀, 240 ₁, . . ., 240 n. In an embodiment, each page may be of the same capacity, e.g.,approximately 4 kilobytes (kB). In another embodiment, some of the pagesmay differ in capacity from other pages within the memory 220.

The memory 220 may be coupled, through the MCH 222, to a decoder 280that may be configured decode data (e.g., payload data) stored in thememory 220, e.g., after the data has been stored in the pages 240 ₀, 240₁, . . . , 240 _(n).

In operation, the processor 210 may receive encrypted digital content260, and the decryption logic 212 may decrypt the encrypted digitalcontent 260 to produce (unencrypted) digital content. The contentstorage logic 224 within the memory management controller 222 may parsethe digital content into one or more portions, e.g., each portioncorresponding to one of the pages 240 ₀, 240 ₁, . . . , 240 _(n). Insome embodiments, the portions may be of equal size. In otherembodiments, at least one portion may differ in size from at least oneof the other portions, with each portion sized to a corresponding one ofthe pages 240 ₀, 240 ₁, . . . , 240 _(n). The content storage logic 224may store each portion into the corresponding page 240 ₀, 240 ₁, . . . ,240 _(n).

The address storage logic 228 within the protection logic 226 of thememory management controller 222 may store a corresponding address of alast written-to memory location within each of the pages 240 ₀, 240 ₁, .. . , 240 _(n) into a corresponding storage register 242 ₀, 242 ₁, . . ., 242 _(n). In an embodiment, each address may be stored as acorresponding offset from an initial address of the corresponding page240 ₀, 240 ₁, . . . , 240 _(n).

The processor 210 may receive program instructions 270. One of theprogram instructions 270 may be a write instruction directed to adestination address that is within one of the pages 240 ₀, 240 ₁, . . ., 240 _(n). For example, the write instruction may have a destinationaddress within page 240 ₀.

The address comparison logic 230 may compare the destination address ofthe write instruction to the address stored in the storage register ofthe corresponding page that includes the destination address, e.g.,storage register 242 ₀. For instance, an offset corresponding to thedestination address may be determined and compared with the last writtenoffset stored in the storage register 242 ₀. If the address comparisonlogic 230 determines that the destination address is less than or equalto the address represented by the offset stored in the storage register240 ₀, then the write instruction, if executed, would overwrite some ofthe stored data in page 240 ₀. Consequently, the address comparisonlogic 230 may trigger the page erase logic 232 to erase the page 240 ₀.Erasure of the page 240 ₀ can ensure that digital content previouslystored in the page will not be subject to unauthorized access that mightoccur, e.g., through an overwrite of a data type indicator that beforethe overwrite indicates that payload data follows.

If the address comparison logic 230 determines that the destinationaddress of the write instruction is subsequent to the last writtenaddress, as determined by comparison of the destination address to astored last written address in a storage register (e.g., by comparisonof the stored offset to an offset corresponding to the destinationaddress), the write may be executed to the destination address of thewrite instruction. Because the destination address has not beenpreviously written, no data will be overwritten as a result of executionof the write instruction.

Turning to FIG. 3, shown is a block diagram of digital content to bestored in a memory, according to an embodiment of the invention.Decrypted digital content 310 may include a first data type indicator302, first data 304, a second data type indicator 306, and second data308. In an embodiment, the first data type indicator 302 may indicatethat the first data 304 is metadata, and the second data type indicator306 may indicate that the second data 308 is payload data.

Memory 320 may include a clear unlocked page 322. Content storage logicwithin a memory management controller (not shown) may write a portion ofthe digital content 310 to the page 322, producing page 324 thatcontains a portion of the digital content 310. After the write to thepage 322 is complete (“first write”), a last written offset, whichcorresponds to a last address of data written the page 324, may bestored in a corresponding storage register (not shown). After completionof the first write, page 324 may be locked to prevent another write tothe page 324.

Subsequently, if an additional write instruction to the page 324 isreceived, an offset corresponding to the destination address of theadditional write instruction may be compared with the last writtenoffset stored in the storage register corresponding to the page 324. Ifthe destination address of the additional write instruction issubsequent to the end of the previous write in page 324 (e.g.,destination address offset of the additional write instruction issubsequent to the stored last written offset) the locked page 324 may beunlocked (e.g., unlocked page 325) and the additional write instructionmay be executed to write additional data to produce page 326, which maybe locked after the additional write instruction is executed. The storedlast written offset may be updated in the corresponding storage registerto reflect the additional data stored in the page 326.

If the comparison of the offset associated with the destination addressof the additional write instruction to the last written offset indicatesthat the additional write instruction is directed to a page address thathas already been written to, contents of the page may be erased(flushed) to produce (clear) page 328. The last written offset may bereset to zero and stored in the storage register corresponding to thepage 328. Erasure of the stored digital content in the page 326 canensure that the previously stored digital content will not be corrupted.

The erased page may be unlocked to enable a subsequent write to page 328that results in page 330, which may again be locked after the subsequentwrite is executed. The stored offset may be updated in the correspondingstorage register of the page 330 to reflect occupied portions of thepage due to the subsequent write.

Turning to FIG. 4, shown is a flow diagram of a method of protectingdigital content, according to an embodiment of the present invention.Beginning at block 402, incoming encrypted digital content may bedecrypted by, e.g., a Security Enhanced Processor, or by a multi-coreprocessor.

Continuing to block 404, the decrypted digital content may be parsedinto portions, e.g., by a memory controller hub. For example, eachportion may be sized to be stored in a page of e.g., isolated memoryregions (IMR) or system memory (e.g., DRAM), and in one embodiment eachpage may have a same storage capacity (e.g., 4 kB), or in anotherembodiment the storage capacity of some of the pages may differ from thestorage capacity of other pages. Some of the pages may be partiallyfilled after the digital content is stored.

Advancing to block 406, each portion may be stored into a correspondingpage within the IMR or system memory. Moving to block 408, a lastwritten offset (corresponding to an address within a page) of a lastwritten memory location within each page, may be stored in acorresponding register that may be located, e.g., in the memorycontroller hub, or in memory, such as the system memory.

Proceeding to block 410, a write instruction may be received (by theprocessor) that has a destination address within one of the pages towhich a digital content portion is stored. Continuing to decisiondiamond 412, a determination may be made by the processor of whether thedestination address of the write instruction is less than or equal tothe last written memory location address within the corresponding page,e.g., by comparison with the stored last written offset. If thedestination address is greater than the last written memory locationaddress, advancing to block 414 the write instruction may be executed,e.g., the write instruction causes additional data to be written to ablank memory location within the corresponding page. Advancing to block418, the stored last written offset of the corresponding page may beupdated to reflect the additional stored data, and continuing to block420, the method ends. If the destination address is less than or equalto the last written memory location address, at block 416 the page maybe erased. Moving to block 417, the last written offset stored in thecorresponding storage register may be reset, to, e.g., zero to reflectthe erased page. Returning to block 414, the write instruction may beexecuted. Advancing to block 418, the stored last written offset of thecorresponding page may be updated to reflect the additional stored data,and continuing to block 420 the method ends.

The method of FIG. 4 can be performed by hardware software, firmware, orcombinations thereof. While shown at a high level in the embodiment ofFIG. 4, it is to be understood that the scope of the present inventionis not so limited.

Embodiments can be implemented in many different systems. For example,embodiments can be realized in a processor such as a multicoreprocessor. Referring now to FIG. 5, shown is a block diagram of aprocessor core in accordance with one embodiment of the presentinvention. As shown in FIG. 5, processor core 500 may be one core of amulticore processor, and is shown as a multi-stage pipelinedout-of-order processor.

As shown in FIG. 5, core 500 includes front end units 510, which may beused to fetch instructions to be executed and prepare them for use laterin the processor. For example, front end units 510 may include a fetchunit 501, an instruction cache 503, and an instruction decoder 505. Insome implementations, front end units 510 may further include a tracecache, along with microcode storage as well as a micro-operationstorage. Fetch unit 501 may fetch macro-instructions, e.g., from memoryor instruction cache 503, and feed them to instruction decoder 505 todecode them into primitives, i.e., micro-operations for execution by theprocessor.

Coupled between front end units 510 and execution units 520 is anout-of-order (OOO) engine 515 that may be used to receive themicro-instructions and prepare them for execution. More specifically OOOengine 515 may include various buffers to re-order micro-instructionflow and allocate various resources needed for execution, as well as toprovide renaming of logical registers onto storage locations withinvarious register files such as register file 530 and extended registerfile 535 such as by using renaming logic of the engine. Register file530 may include separate register files for integer and floating pointoperations. Extended register file 535 may provide storage forvector-sized units, e.g., 256 or 512 bits per register.

Various resources may be present in execution units 520, including, forexample, various integer, floating point, and single instructionmultiple data (SIMD) logic units, among other specialized hardware. Forexample, such execution units may include one or more arithmetic logicunits (ALUs) 522. Of course other execution units such asmultiply-accumulate units and so forth may further be present. Resultsmay be provided to a retirement logic, which may be implemented within amemory subsystem 560 of the processor. Various processor structuresincluding execution units and front end logic, for example, may becoupled to a memory subsystem 560. This memory subsystem may provide aninterface between processor structures and further portions of a memoryhierarchy, e.g., an on or off-chip cache and a system memory. As seenthe subsystem has various components including a memory order buffer(MOB) 540. More specifically, MOB 540 may include various arrays andlogic to receive information associated with instructions that areexecuted. This information is then examined by MOB 540 to determinewhether the instructions can be validly retired and result datacommitted to the architectural state of the processor, or whether one ormore exceptions occurred that prevent a proper retirement of theinstructions. Of course, MOB 540 may handle other operations associatedwith retirement.

As shown in FIG. 5, MOB 540 is coupled to a cache 550 which, in oneembodiment may be a low level cache (e.g., an L1 cache). Memorysubsystem 560 also may include an integrated memory controller 570 toprovide for communication with a system memory (not shown for ease ofillustration in FIG. 5). Memory subsystem 560 may further include amemory execution unit (MEU) 575 that handles various operations toinitiate memory requests and handle return of data from memory. Forexample, MEU 575 may effect parsing of digital content into portions,storage of the portions into corresponding pages, storage of a lastwritten offset of each page, and determination of whether a writeinstruction is directed to a memory location that includes digitalcontent within a page. If the write instruction is directed to a memorylocation storing digital content within a page, the MEU 575 may erasethe page that includes the destination memory location, as describedherein with regard to embodiments of the invention.

From memory subsystem 560, data communication may occur with higherlevel caches, system memory and so forth. While shown with this highlevel in the embodiment of FIG. 5, understand the scope of the presentinvention is not limited in this regard. For example, while theimplementation of FIG. 5 is with regard to an out-of-order machine suchas of a so-called x86 instruction set architecture (ISA) architecture,the scope of the present invention is not limited in this regard. Thatis, other embodiments may be implemented in an in-order processor, areduced instruction set computing (RISC) processor such as an ARM-basedprocessor, or a processor of another type of ISA that can emulateinstructions and operations of a different ISA via an emulation engineand associated logic circuitry.

Referring now to FIG. 6, shown is a block diagram of a processor inaccordance with an embodiment of the present invention. As shown in FIG.6, processor 600 may be a multicore processor including a plurality ofcores 610 _(a)-610 _(n) in a core domain 610. In one embodiment, eachcore may include a memory execution unit (not shown) that includescontent storage logic, address storage logic, address comparison logic,and page erase logic, as described herein in embodiments of theinvention. As further shown in FIG. 6, one or more graphics processingunits (GPUs) 612 ₀-612 _(n) may be present in a graphics domain 612.These various compute elements may be coupled via an interconnect 615 toa system agent or uncore 620 that includes various components. As seen,the uncore 620 may include a shared cache 630 which may be a last levelcache.

In addition, the uncore may include an integrated memory controller 640and various interfaces 650. In some embodiments of the presentinvention, the memory controller 640 may parse decrypted digital contentinto portions, store the portions in corresponding pages of a systemmemory 660, and store a last written offset of each page. The memorycontroller 640 may determine whether a write instruction has adestination address of a memory location to which some of the digitalcontent is stored within one of the pages, and if so, may erase thepage, according to embodiments of the present invention.

With further reference to FIG. 6, processor 600 may communicate with thesystem memory 660, e.g., via a memory bus. In addition, by interfaces650, connection can be made to various off-chip components such asperipheral devices, mass storage and so forth. While shown with thisparticular implementation in the embodiment of FIG. 6, the scope of thepresent invention is not limited in this regard.

Referring now to FIG. 7, shown is a block diagram of a multi-domainprocessor in accordance with another embodiment of the presentinvention. As shown in the embodiment of FIG. 7, processor 700 includesmultiple domains. Specifically, a core domain 710 can include aplurality of cores 710 ₀-710 _(n), a graphics domain 720 can include oneor more graphics engines, and a system agent domain 750 may further bepresent.

Note that while only shown with three domains, understand the scope ofthe present invention is not limited in this regard and additionaldomains can be present in other embodiments. For example, multiple coredomains may be present, each including at least one core.

In general, each core 710 may further include low level caches inaddition to various execution units and additional processing elements.The various cores may be coupled to each other and to a shared cachememory formed of a plurality of units of a last level cache (LLC) 740₀-740 _(n). In various embodiments, LLC 740 may be shared amongst thecores and the graphics engine, as well as various media processingcircuitry. As seen, a ring interconnect 730 thus couples the corestogether, and provides interconnection between the cores, graphicsdomain 720 and system agent circuitry 750.

In the embodiment of FIG. 7, system agent domain 750 may include displaycontroller 752 which may provide control of and an interface to anassociated display. As further seen, system agent domain 750 may includea power control unit 755.

As further seen in FIG. 7, processor 700 can further include anintegrated memory controller (IMC) 770 that can provide for an interfaceto a system memory (not shown), such as a dynamic random access memory(DRAM). The IMC 770 may parse decrypted digital content into portions,store the portions in corresponding pages of the system memory, andstore a last written offset of each page, in accordance with embodimentsof the present invention. The IMC 770 may determine whether a writeinstruction has a destination address of a memory location to which someof the digital content is stored within one of the pages (e.g., throughcomparison of a representation of the destination address with the lastwritten offset of the page), and if so, may erase the page, according toembodiments of the present invention.

Multiple interfaces 780 ₀-780 _(n) may be present to enableinterconnection between the processor and other circuitry. For example,in one embodiment at least one direct media interface (DMI) interfacemay be provided as well as one or more Peripheral Component InterconnectExpress (PCI Express™ (PCIe™)) interfaces. Still further, to provide forcommunications between other agents such as additional processors orother circuitry, one or more interfaces in accordance with a Intel®Quick Path Interconnect (QPI) protocol may also be provided. Althoughshown at this high level in the embodiment of FIG. 7, understand thescope of the present invention is not limited in this regard.

Referring to FIG. 8, an embodiment of a processor including multiplecores is illustrated. Processor 800 includes any processor or processingdevice, such as a microprocessor, an embedded processor, a digitalsignal processor (DSP), a network processor, a handheld processor, anapplication processor, a co-processor, a system on a chip (SOC), orother device to execute code. Processor 800, in one embodiment, includesat least two cores—cores 801 and 802, which may include asymmetric coresor symmetric cores (the illustrated embodiment). However, processor 800may include any number of processing elements that may be symmetric orasymmetric.

In one embodiment, a processing element refers to hardware or logic tosupport a software thread. Examples of hardware processing elementsinclude: a thread unit, a thread slot, a thread, a process unit, acontext, a context unit, a logical processor, a hardware thread, a core,and/or any other element, which is capable of holding a state for aprocessor, such as an execution state or architectural state. In otherwords, a processing element, in one embodiment, refers to any hardwarecapable of being independently associated with code, such as a softwarethread, operating system, application, or other code. A physicalprocessor typically refers to an integrated circuit, which potentiallyincludes any number of other processing elements, such as cores orhardware threads.

A core often refers to logic located on an integrated circuit capable ofmaintaining an independent architectural state, wherein eachindependently maintained architectural state is associated with at leastsome dedicated execution resources. In contrast to cores, a hardwarethread typically refers to any logic located on an integrated circuitcapable of maintaining an independent architectural state, wherein theindependently maintained architectural states share access to executionresources. As can be seen, when certain resources are shared and othersare dedicated to an architectural state, the line between thenomenclature of a hardware thread and core overlaps. Yet often, a coreand a hardware thread are viewed by an operating system as individuallogical processors, where the operating system is able to individuallyschedule operations on each logical processor.

Physical processor 800, as illustrated in FIG. 8, includes two cores,cores 801 and 802. Here, cores 801 and 802 are considered symmetriccores, i.e., cores with the same configurations, functional units,and/or logic. In another embodiment, core 801 includes an out-of-orderprocessor core, while core 802 includes an in-order processor core.However, cores 801 and 802 may be individually selected from any type ofcore, such as a native core, a software managed core, a core adapted toexecute a native instruction set architecture (ISA), a core adapted toexecute a translated ISA, a co-designed core, or other known core. Yetto further the discussion, the functional units illustrated in core 801are described in further detail below, as the units in core 802 operatein a similar manner.

As depicted, core 801 includes two hardware threads 801 a and 801 b,which may also be referred to as hardware thread slots 801 a and 801 b.Therefore, software entities, such as an operating system, in oneembodiment potentially view processor 800 as four separate processors,i.e., four logical processors or processing elements capable ofexecuting four software threads concurrently. As alluded to above, afirst thread is associated with architecture state registers 801 a, asecond thread is associated with architecture state registers 801 b, athird thread may be associated with architecture state registers 802 a,and a fourth thread may be associated with architecture state registers802 b. Here, each of the architecture state registers (801 a, 801 b, 802a, and 802 b) may be referred to as processing elements, thread slots,or thread units, as described above. As illustrated, architecture stateregisters 801 a are replicated in architecture state registers 801 b, soindividual architecture states/contexts are capable of being stored forlogical processor 801 a and logical processor 801 b. In core 801, othersmaller resources, such as instruction pointers and renaming logic inallocator and renamer block 830 may also be replicated for threads 801 aand 801 b. Some resources, such as re-order buffers inreorder/retirement unit 835, ILTB 820, load/store buffers, and queuesmay be shared through partitioning. Other resources, such as generalpurpose internal registers, page-table base register(s), low-leveldata-cache and data-TLB 815, execution unit(s) 840, and portions ofout-of-order unit 835 are potentially fully shared.

Processor 800 often includes other resources, which may be fully shared,shared through partitioning, or dedicated by/to processing elements. InFIG. 8, an embodiment of a purely exemplary processor with illustrativelogical units/resources of a processor is illustrated. Note that aprocessor may include, or omit, any of these functional units, as wellas include any other known functional units, logic, or firmware notdepicted. As illustrated, core 801 includes a simplified, representativeout-of-order (OOO) processor core. But an in-order processor may beutilized in different embodiments. The OOO core includes a branch targetbuffer 820 to predict branches to be executed/taken and aninstruction-translation buffer (I-TLB) 820 to store address translationentries for instructions.

Core 801 further includes decode module 825 coupled to fetch unit 820 todecode fetched elements. Fetch logic, in one embodiment, includesindividual sequencers associated with thread slots 801 a, 801 b,respectively. Usually core 801 is associated with a first ISA, whichdefines/specifies instructions executable on processor 800. Oftenmachine code instructions that are part of the first ISA include aportion of the instruction (referred to as an opcode), whichreferences/specifies an instruction or operation to be performed. Decodelogic 825 includes circuitry that recognizes these instructions fromtheir opcodes and passes the decoded instructions on in the pipeline forprocessing as defined by the first ISA. For example, decoders 825, inone embodiment, include logic designed or adapted to recognize specificinstructions, such as transactional instruction. As a result of therecognition by decoders 825, the architecture or core 801 takesspecific, predefined actions to perform tasks associated with theappropriate instruction. It is important to note that any of the tasks,blocks, operations, and methods described herein may be performed inresponse to a single or multiple instructions; some of which may be newor old instructions.

In one example, allocator and renamer block 830 includes an allocator toreserve resources, such as register files to write instructionprocessing results. However, threads 801 a and 801 b are potentiallycapable of out-of-order execution, where allocator and renamer block 830also reserves other resources, such as reorder buffers to trackinstruction results. Unit 830 may also include a register renamer torename program/instruction reference registers to other registersinternal to processor 800. Reorder/retirement unit 835 includescomponents, such as the reorder buffers mentioned above, load buffers,and store buffers, to support out-of-order execution and later in-orderretirement of instructions executed out-of-order.

Scheduler and execution unit(s) block 840, in one embodiment, includes ascheduler unit to schedule instructions/operation on execution units.For example, a floating point instruction is scheduled on a port of anexecution unit that has an available floating point execution unit.Register files associated with the execution units are also included tostore information instruction processing results. Exemplary executionunits include a floating point execution unit, an integer executionunit, a jump execution unit, a load execution unit, a store executionunit, and other known execution units.

Lower level data cache and data translation buffer (D-TLB) 850 arecoupled to execution unit(s) 840. The data cache is to store recentlyused/operated on elements, such as data operands, which are potentiallyheld in memory coherency states. The D-TLB is to store recentvirtual/linear to physical address translations.

Here, cores 801 and 802 share access to higher-level or further-outcache 810, which is to cache recently fetched elements. Note thathigher-level or further-out refers to cache levels increasing or gettingfurther away from the execution unit(s). In one embodiment, higher-levelcache 810 is a last-level data cache—last cache in the memory hierarchyon processor 800—such as a second or third level data cache. However,higher level cache 810 is not so limited, as it may be associated withor includes an instruction cache. A trace cache—a type of instructioncache—instead may be coupled after decoder 825 to store recently decodedtraces.

In the depicted configuration, processor 800 also includes, controller870. The controller 870 may parse decrypted digital content intoportions and store the portions in corresponding pages of a systemmemory 875 in accordance with embodiments of the present invention. Thecontroller 870 may determine whether a write instruction has adestination address of a memory location to which some of the digitalcontent is stored within one of the pages (e.g., through comparison of arepresentation of the destination address with a last written offset ofthe page), and if so, may erase the page, according to embodiments ofthe present invention.

In this scenario, bus interface 805 is to communicate with devicesexternal to processor 800, such as the system memory 875, a chipset(often including a memory controller hub to connect to memory 875 and anI/O controller hub to connect peripheral devices), a memory controllerhub, a northbridge, or other integrated circuit (not shown). And in thisscenario, bus 805 may include any known interconnect, such as multi-dropbus, a point-to-point interconnect, a serial interconnect, a parallelbus, a coherent (e.g. cache coherent) bus, a layered protocolarchitecture, a differential bus, and a GTL bus.

Memory 875 may be dedicated to processor 800 or shared with otherdevices in a system. Common examples of types of memory 875 includeDRAM, SRAM, non-volatile memory (NV memory), and other known storagedevices. Note that device 880 may include a graphic accelerator,processor or card coupled to a memory controller hub, data storagecoupled to an I/O controller hub, a wireless transceiver, a flashdevice, an audio controller, a network controller, or other knowndevice.

Note that in the depicted embodiment, the controller 870 is illustratedas part of processor 800. Recently, as more logic and devices are beingintegrated on a single die, such as SOC, each of these devices may beincorporated on processor 800. For example in one embodiment, memorycontroller hub 870 is on the same package and/or die with processor 800.Here, a portion of the core (an on-core portion) includes the controller870 for interfacing with other devices such as memory 875 or a graphicsdevice 880. The configuration, including an interconnect and controllersfor interfacing with such devices, is often referred to as an on-core(or un-core configuration). As an example, bus interface 805 includes aring interconnect with a memory controller for interfacing with memory875 and a graphics controller for interfacing with graphics processor880. Yet, in the SOC environment, even more devices, such as the networkinterface, co-processors, memory 875, graphics processor 880, and anyother known computer devices/interface may be integrated on a single dieor integrated circuit to provide small form factor with highfunctionality and low power consumption.

Embodiments may be implemented in many different system types. Referringnow to FIG. 9, shown is a block diagram of a system in accordance withan embodiment of the present invention. As shown in FIG. 9,multiprocessor system 900 is a point-to-point interconnect system, andincludes a first processor 970 and a second processor 980 coupled via apoint-to-point interconnect 950. As shown in FIG. 9, each of processors970 and 980 may be multicore processors, including first and secondprocessor cores (i.e., processor cores 974 a and 974 b and processorcores 984 a and 984 b), although potentially many more cores may bepresent in the processors. Each of the processors may include arespective cache. First processor 970 and second processor 980 may becoupled to a chipset 990 via P-P interconnects 952 and 954,respectively. As shown in FIG. 9, chipset 990 includes P-P interfaces994 and 998.

Still referring to FIG. 9, first processor 970 further includes a memorycontroller hub (MCH) 972 and point-to-point (P-P) interfaces 976 and978. Similarly, second processor 980 includes a MCH 982 and P-Pinterfaces 986 and 988. As shown in FIG. 9, MCH's 972 and 982 couple theprocessors to respective memories, namely a memory 932 and a memory 934,which may be portions of system memory (e.g., DRAM) locally attached tothe respective processors. Each of the MCH's 972 and 982 may parsedecrypted digital content into portions and store the portions incorresponding pages of the corresponding memory (932 or 934), inaccordance with embodiments of the present invention. The MCHs 972 and982 may determine whether a write instruction has a destination addressof a memory location to which some of the digital content is storedwithin one of the pages (e.g., through comparison of a representation ofthe destination address with a last written offset of the page), and ifso, may erase the page, according to embodiments of the presentinvention.

Furthermore, chipset 990 includes an interface 992 to couple chipset 990with a high performance graphics engine 938 by a P-P interconnect 939.In turn, chipset 990 may be coupled to a first bus 916 via an interface996. As shown in FIG. 9, various input/output (I/O) devices 914 may becoupled to first bus 916, along with a bus bridge 918 which couplesfirst bus 916 to a second bus 920. Various devices may be coupled tosecond bus 920 including, for example, a keyboard/mouse 922,communication devices 926 and a data storage unit 928 such as a diskdrive or other mass storage device, in one embodiment. Further, an audioI/O 924 may be coupled to second bus 920. Embodiments can beincorporated into other types of systems including mobile devices suchas a smart cellular telephone, Ultrabook™, tablet computer, netbook, orso forth.

That is, in other embodiments, a processor architecture may includeemulation features such that the processor can execute instructions of afirst ISA, referred to as a source ISA, where the architecture isaccording to a second ISA, referred to as a target ISA. In general,software, including both the OS and application programs, is compiled tothe source ISA, and hardware implements the target ISA designedspecifically for a given hardware implementation with specialperformance and/or energy efficiency features.

Referring to FIG. 10, a block diagram of a system 1000 is shown inaccordance with another embodiment of the present invention. The system1000 includes a processor 1010 and memory 1030. The processor 1010 maybe a system on a chip (SOC) and may include a security engine 1012, acore unit 1014 that may include one or more cores, cache memory and aninterface to communicate with other SOC components, storage 1016, andencode/decode logic 1018.

In operation, the security engine 1012 may decrypt incoming encrypteddata 1020. The security engine 1012 may parse the (unencrypted) datainto portions and may store the portions in corresponding pages withinthe memory 1030. The security engine 1012 may store a last writtenoffset corresponding to a last written address of each page, in acorresponding storage register. In one embodiment, the storage registersmay be located within the processor 1010. In another embodiment thestorage registers may be located within the memory 1030.

The Core unit 1014 may receive a write instruction whose destinationaddress lies in one of the pages. The security engine 1012 may perform acomparison of the last written offset to a write offset associated withthe destination address of the write instruction. The security engine1012 may lock or unlock write access to the page based on the comparisonof the last written offset to the write offset. For example, if thewrite offset is larger than the last written offset, the security engine1012 may unlock write access to the corresponding page, and if the writeoffset is less than or equal to the last written offset, the securityengine 1012 may lock write access to the corresponding page, reset thelast written offset to zero, and erase (e.g., flush) contents of thecorresponding page.

Embodiments may be used in many different types of systems. For example,in one embodiment a communication device can be arranged to perform thevarious methods and techniques described herein. Embodiments can beincorporated into other types of systems including mobile devices suchas a smart cellular telephone, tablet computer, netbook, Ultrabook™, orso forth. Of course, the scope of the present invention is not limitedto a communication device, and instead other embodiments can be directedto other types of apparatus for processing instructions, or one or moremachine readable media including instructions that in response to beingexecuted on a computing device, cause the device to carry out one ormore of the methods and techniques described herein.

The following examples pertain to further embodiments. In an embodiment,a processor includes content storage logic to parse digital content intoportions and cause each portion to be stored into a corresponding pageof a memory. The processor also includes protection logic to receive awrite instruction having a destination address within the memory. If thedestination address is associated with a memory location that storessome of the digital content, the protection logic is to erase the pageassociated with the memory location, and if the destination address isassociated with another memory location that does not store any of thedigital content, the protection logic is to permit execution of thewrite instruction.

In another embodiment, the processor includes decryption logic todecrypt encrypted digital content and to output the digital content tothe content storage logic.

In an embodiment, each page has a same page size.

In an embodiment, the processor includes one or more storages, eachstorage to store a representation of a last written address of acorresponding page. In an embodiment, the representation of the lastwritten address includes an offset from an initial address of thecorresponding page.

The protection logic may compare a representation of the destinationaddress to the representation of the last written address stored in oneof the storages to determine whether the memory storage locationassociated with the destination address stores some of the digitalcontent and if the destination address is greater than the last writtenaddress, the protection logic may determine that the memory storagelocation associated with the destination address does not store any ofthe digital content and the protection logic may permit execution of thewrite instruction.

If the destination address lies between a beginning of a particular pageand the last written address, the protection logic may erase contents ofthe particular page and may reset the representation of the last writtenaddress.

In an embodiment, a system includes a processor, dynamic random accessmemory (DRAM) coupled to the processor, and a memory controller coupledto the DRAM to write digital content into a plurality of pages in theDRAM. Responsive to receipt by the processor of a write instructionhaving a destination address of a memory storage location in one of thepages, the memory controller may, if the memory storage location doesnot store any of the digital content, execute the write instruction, andif the memory storage location stores some of the digital content, erasethe page.

In an embodiment, the memory controller includes a plurality ofregisters, each register to store a last written offset corresponding toa last written address of a corresponding page.

In an embodiment, the memory controller may compare a destination offsetcorresponding to the destination address to the offset stored in one ofthe registers to determine whether the memory storage locationassociated with the destination address stores some of the digitalcontent. If the destination offset lies between a beginning of aparticular page and the last written offset, the memory controller maydetermine that the memory storage location associated with thedestination address stores some of the digital content.

If the memory storage location stores some of the digital content, thememory controller may reset the last written offset after the page iserased. If the destination offset is greater than the last writtenoffset, the memory controller may determine that the memory storagelocation associated with the destination address does not store any ofthe digital content.

In an embodiment, a method includes parsing digital content intoportions, storing each portion into a corresponding page of a memory,comparing a destination address of a write instruction to a last writtenaddress of one of the pages to determine whether a corresponding memorylocation stores some of the digital content, erasing at least one of thepages if the corresponding memory location stores some of the digitalcontent, and executing the write instruction if the corresponding memorylocation does not store any of the digital content.

The method may further include decrypting the digital content prior toparsing the digital content.

Comparing may include determining that a first page includes thedestination address and if the destination address is between a firstwritten address of the first page and the last written address of thefirst page, determining that the corresponding memory location storessome of the digital content.

The method may include, if the destination address is not between thefirst written address of the first page and the last written address ofthe first page, determining that the corresponding memory location doesnot store any of the digital content. The method may further includeupdating the corresponding last written address in response to executionof the write instruction.

In an embodiment, at least one machine readable medium includes one ormore instructions that when executed on a processor configure theprocessor to carry out one or more of the aforementioned embodiments ofthe method.

In an embodiment, an apparatus may be configured to perform one or moreof the aforementioned embodiments of the method.

In an embodiment, an apparatus includes means for performing the methodof any of the aforementioned embodiments of the method.

In an embodiment, a processor may include one or more cores andprotection logic to determine whether to unlock write access to a firstpage of a memory responsive to a comparison of a write offset that isassociated with a write instruction to the first page to a last writtenoffset that is stored in a first storage and that is associated with alast written memory location of the first page. The protection logic mayunlock the write access to the first page and permit execution of thewrite instruction responsive to the comparison that indicates that thewrite offset exceeds the last written offset.

The processor may include update logic to replace the last writtenoffset in the first storage with the write offset responsive to theexecution of the write instruction.

The protection logic may erase the first page responsive to thecomparison that indicates that the write offset is less than or equal tothe last written offset.

The processor may include update logic to reset the last written offsetin the first storage after erasure of the page.

Embodiments may be implemented in code and may be stored on anon-transitory storage medium having stored thereon instructions whichcan be used to program a system to perform the instructions. The storagemedium may include, but is not limited to, any type of disk includingfloppy disks, optical disks, solid state drives (SSDs), compact diskread-only memories (CD-ROMs), compact disk rewritables (CD-RWs), andmagneto-optical disks, semiconductor devices such as read-only memories(ROMs), random access memories (RAMs) such as dynamic random accessmemories (DRAMs), static random access memories (SRAMs), erasableprogrammable read-only memories (EPROMs), flash memories, electricallyerasable programmable read-only memories (EEPROMs), magnetic or opticalcards, or any other type of media suitable for storing electronicinstructions.

While the present invention has been described with respect to a limitednumber of embodiments, those skilled in the art will appreciate numerousmodifications and variations therefrom. It is intended that the appendedclaims cover all such modifications and variations as fall within thetrue spirit and scope of this present invention.

What is claimed is:
 1. A processor comprising: content storage logic toparse digital content into portions and cause each portion to be storedinto a corresponding page of a memory; and protection logic to: receivea write instruction having a destination address within the memory; ifthe destination address is associated with a memory location that storessome of the digital content, erase the page associated with the memorylocation; if the destination address is associated with another memorylocation that does not store any of the digital content, permitexecution of the write instruction.
 2. The processor of claim 1, furthercomprising decryption logic to decrypt encrypted digital content and tooutput the digital content to the content storage logic.
 3. Theprocessor of claim 1, wherein each page has a same page size.
 4. Theprocessor of claim 1, further comprising one or more storages, eachstorage to store a representation of a last written address of acorresponding page.
 5. The processor of claim 4, wherein therepresentation of the last written address comprises an offset from aninitial address of the corresponding page.
 6. The processor of claim 4,wherein the protection logic is to compare a representation of thedestination address to the representation of the last written addressstored in one of the storages to determine whether the memory storagelocation associated with the destination address stores some of thedigital content.
 7. The processor of claim 6, wherein if the destinationaddress is greater than the last written address, the protection logicis to determine that the memory storage location associated with thedestination address does not store any of the digital content and theprotection logic is to permit execution of the write instruction.
 8. Theprocessor of claim 6, wherein if the destination address lies between abeginning of a particular page and the last written address, theprotection logic is to erase the particular page.
 9. The processor ofclaim 8, wherein the processor is to reset the representation of thelast written address after erasure of the particular page.
 10. A systemcomprising: a processor; dynamic random access memory (DRAM) coupled tothe processor; and a memory controller coupled to the DRAM, the memorycontroller to write digital content into a plurality of pages in theDRAM, wherein responsive to receipt by the processor of a writeinstruction having a destination address of a memory storage location inone of the pages, the memory controller is to: if the memory storagelocation does not store any of the digital content, execute the writeinstruction; and if the memory storage location stores some of thedigital content, erase the page.
 11. The system of claim 10, wherein thememory controller includes a plurality of registers, each register tostore a last written offset corresponding to a last written address of acorresponding page.
 12. The system of claim 11, wherein the memorycontroller is to compare a destination offset corresponding to thedestination address to the offset stored in one of the registers todetermine whether the memory storage location associated with thedestination address stores some of the digital content.
 13. The systemof claim 12, wherein if the destination offset lies between a beginningof a particular page and the last written offset, the memory controlleris to determine that the memory storage location associated with thedestination address stores some of the digital content.
 14. The systemof claim 11, wherein if the memory storage location stores some of thedigital content, the memory controller is to reset the last writtenoffset.
 15. The system of claim 12, wherein if the destination offset isgreater than the last written offset, the memory controller is todetermine that the memory storage location associated with thedestination address does not store any of the digital content.
 16. Amethod comprising: parsing digital content into portions; storing eachportion into a corresponding page of a memory; comparing a destinationaddress of a write instruction to a last written address of one of thepages to determine whether a corresponding memory location stores someof the digital content; erasing at least one of the pages if thecorresponding memory location stores some of the digital content; andexecuting the write instruction if the corresponding memory locationdoes not store any of the digital content.
 17. The method of claim 16,further comprising decrypting the digital content prior to parsing thedigital content.
 18. The method of claim 16, wherein the comparingcomprises: determining that a first page includes the destinationaddress; if the destination address is between a first written addressof the first page and the last written address of the first page,determining that the corresponding memory location stores some of thedigital content; and if the destination address is not between the firstwritten address of the first page and the last written address of thefirst page, determining that the corresponding memory location does notstore any of the digital content.
 19. The method of claim 16, furthercomprising updating the corresponding last written address in responseto execution of the write instruction.
 20. A processor comprising: oneor more cores; and protection logic to unlock write access to a firstpage of a memory responsive to a comparison of a write offset associatedwith a write instruction to the first page to a last written offsetstored in a first storage and associated with a last written memorylocation of the first page.
 21. The processor of claim 20, wherein theprotection logic is to unlock the write access to the first page and topermit execution of the write instruction responsive to the comparisonthat indicates that the write offset exceeds the last written offset.22. The processor of claim 21, further comprising update logic toreplace the last written offset in the first storage with the writeoffset responsive to the execution of the write instruction.
 23. Theprocessor of claim 20, wherein the protection logic is to erase thefirst page responsive to the comparison that indicates that the writeoffset is less than or equal to the last written offset.
 24. Theprocessor of claim 23, further comprising update logic to reset the lastwritten offset in the first storage responsive to the comparison thatindicates that the write offset is less than or equal to the lastwritten offset.